Nautilus 1992 July/Nautilus-3-8/Nautilus-3-8.bin/Tools & Utilities/Techy Stuff/Doco ƒ/CSMP ƒ/CSMP-V1-097.TXT

Text File | 1992-06-30 | 34.1 KB | 967 lines

C.S.M.P. Digest             Wed, 27 May 92       Volume 1 : Issue 97

Today's Topics:

    *** NEEDED: 24-Bit graphics sources, or help!!!  ***
    Do Prograph/Serius do video?
    Prograph mailing list.
    Mac Pascal Programming Primer (book review and comments)
    List Box LDEF with icons
    Precompiled version of MacApp.h
    ResEdit and 7.0


The Comp.Sys.Mac.Programmer Digest is moderated by Michael A. Kelly.

These digests are available (by using FTP, account anonymous, your email
address as password) in the pub/mac/csmp-digest directory on ftp.cs.uoregon.
edu.  This is also the home of the comp.sys.mac.programmer Frequently Asked
Questions list.  The last several issues of the digest are available from
sumex-aim.stanford.edu as well.

These digests are also available via email.  Just send a note saying that you
want to be on the digest mailing list to [e-mail], and you will
automatically receive each new digest as it is created.

The digest is a collection of articles from the internet newsgroup comp.sys.
mac.programmer.  It is designed for people who read c.s.m.p. semi-regularly
and want an archive of the discussions.  If you don't know what a newsgroup
is, you probably don't have access to it.  Ask your systems administrator(s)
for details.  (This means you can't post questions to the digest.)

The articles in these digests are taken directly from comp.sys.mac.programmer.
They are not edited; all articles included in this digest are in their original
posted form.  The only articles that are -not- included in these digests are
those which didn't receive any replies (except those that give information
rather than ask a question).  All replies to each article are concatenated
onto the original article in the order in which they were received.  Article
threads are not added to the digests until the last article added to the
thread is at least one month old (this is to ensure that the thread is dead
before adding it to the digests).

Send administrative mail to [e-mail].

-------------------------------------------------------

From: [e-mail] (John F. Talarico)
Subject: *** NEEDED: 24-Bit graphics sources, or help!!!  ***
Date: 24 Apr 92 19:12:06 GMT
Organization: Syracuse University, Syracuse, NY

HELP!!

    I need help producing 24-bit images on a Mac IIfx w/ ThinkPascal 4.0.

I was wondering if anyone had any examples of code that draw images in 24-bit
color like Mandelbrot sets, etc.  I only need the sections that sets up the
palette, and accesses each individual color by # (i.e. black =0 and misc.color
(maximum intensity) = somelargenumber).

I would like some information soon.... Finals are around the corner  ;)


If this means anything to anyone, I'm using it to produce 2-D graphs of the
logistic function's Lyapunov exponent.  I want to plot many (more than 256)
different intensity/saturation levels of one hue.

Thanx in advance...
JT

(Cogito Ergo Pingo)


- --
_______________________________________________________________________________
"... I speak                   |    I am:  John Talarico  (Elvis-at-large)
       for the                 |  I'm at:  Syracuse University  (Prison)
__________trees. "__the Lorax__|  a.k.a.:  [e-mail] (Go figure)

+++++++++++++++++++++++++++

From: [e-mail] (Mark Lanett)
Date: 25 Apr 92 23:32:29 GMT
Organization: University of Illinois at Urbana

[e-mail] (John F. Talarico) writes:

>HELP!!
>
>    I need help producing 24-bit images on a Mac IIfx w/ ThinkPascal 4.0.

>I was wondering if anyone had any examples of code that draw images in 24-bit
>color like Mandelbrot sets, etc.  I only need the sections that sets up the
>palette, and accesses each individual color by # (i.e. black =0 and misc.color
>(maximum intensity) = somelargenumber).

Er, um, 24-bit images are "direct," i.e. they don't use palettes. Neither do
16-bit images, though I'd prefer it if they did. Just turn your values into
RGB and plot them directly. In no particular language or toolbox:
    plot( x,y,color(value,value,value)) // gives you grayscale
- --
Mark Lanett, Software Tools Group, NCSA; [e-mail]; NCSA.STG (AppleLink)

---------------------------

From: [e-mail] (Terry Thiel)
Subject: Do Prograph/Serius do video?
Organization: University of Illinois at Urbana
Date: Wed, 22 Apr 1992 23:13:55 GMT

We are working on a project that requires an app that will handle cutting and
pasting video and filing shots into a database.  I need to be able to customize
this database in many different ways.  Does Serius or Prograph have a video
module of some sort?  I know that either one will be perfect for the database
but it would be great if they also had video capabilities.  Thanks for any
info.
- -Terry

+++++++++++++++++++++++++++

From: [e-mail] (Tim Bates)
Date: Sat, 25 Apr 1992 02:56:49 GMT
Organization: University of Auckland, New Zealand.

[e-mail] (Terry Thiel) writes:

>We are working on a project that requires an app that will handle cutting and
>pasting video and filing shots into a database.  I need to be able to customize
>this database in many different ways.  Does Serius or Prograph have a video
>module of some sort?  I know that either one will be perfect for the database
>but it would be great if they also had video capabilities.  Thanks for any
>info.
>-Terry

No idea about Serius.

Prograph has a working database application that comes as an example program.
It also supports quicktime calls. Therefore you can show video in a database
quite easily.

tim bates

+++++++++++++++++++++++++++

From: [e-mail] (Thomas A. Creedon)
Date: 24 Apr 92 22:26:03 GMT
Organization: Oregon Hearing Research Center

In article <[e-mail]>, [e-mail] (Terry Thiel) writes:
>
> We are working on a project that requires an app that will handle cutting and
> pasting video and filing shots into a database.  I need to be able to customize
> this database in many different ways.  Does Serius or Prograph have a video
> module of some sort?  I know that either one will be perfect for the database
> but it would be great if they also had video capabilities.  Thanks for any
> info.
> -Terry
>
>

Prograph has an extension to work with Quicktime.  I've been using
Prograph for the last several months and find working with it
enjoyable.  I can't give you a comparison between Prograph and Serius.

Toodle-looooooooo........
Thomas
[e-mail]

---------------------------

From: [e-mail] (Terry Thiel)
Subject: Prograph mailing list.
Date: 24 Apr 92 19:50:32 GMT
Organization: University of Illinois at Urbana

How do you get on the Prograph mailing list?  I was on it but need to get back
on since I will be doing some developing with Prograph.  Has there been any
consideration of a Prograph newsgroup?
- -Terry

+++++++++++++++++++++++++++

From: [e-mail] (Mel Walker)
Organization: Novell, Inc. - Walnut Creek
Date: Fri, 24 Apr 1992 22:28:52 GMT

In article <[e-mail]> [e-mail] (Terry Thiel) writes:
>How do you get on the Prograph mailing list?  I was on it but need to get back
>on since I will be doing some developing with Prograph.  Has there been any
>consideration of a Prograph newsgroup?
>-Terry

I would like to know as well.
Thanks,
- --Mel Walker
[e-mail]

+++++++++++++++++++++++++++

From: [e-mail] (Tim Bates)
Date: Sat, 25 Apr 1992 03:02:10 GMT
Organization: University of Auckland, New Zealand.

[e-mail] (Mel Walker) writes:

>(Terry Thiel) writes:
>>How do you get on the Prograph mailing list?
>>stuff deleted
>>consideration of a Prograph newsgroup?
>>-Terry
>I would like to know as well.
>Thanks,
>--Mel Walker
>[e-mail]

the prograph list is <[e-mail]>

I would like a Prograph newsgroup also, mainly for the chance to grow
the communicating Prograph user community.
I guess there is nothing stopping anyone writing directly to com.mac.prog
with Prograph questions.


tim bates


---------------------------

From: [e-mail] (Tom Verhoeff)
Subject: Mac Pascal Programming Primer (book review and comments)
Date: 26 Apr 92 13:38:37 GMT


Short review of and comments on:

    Macintosh Pascal Programming Primer, Volume I
    Inside the Toolbox Using THINK Pascal
    by Dave Mark & Cartwright Reed
    Addison-Wesley, 1991
    ISBN 0-201-57084-X


Review
- ------

This book is aimed at the beginning Mac-programmer, not the beginning
programmer.  It assumes you are familiar with Pascal, though not
necessarily THINK Pascal.  You learn how to build some basic
stand-alone applications.  It covers the particular aspects of THINK
Pascal (version 3) needed for this and also introduces you to ResEdit
(version 2.0).  But the bulk of the material is concerned with the Mac
Toolbox and Operating System.

The book does not overwhelm you with the ins and outs of every Toolbox
routine.  The intention is to get you started right away.  It sketches
the big picture and illustrates each topic in isolation with a minimal,
but real, stand-alone application.  The integration of all these bits
and pieces into full-blown applications is left to the reader's
imagination.  For more detailed information you are often referred to
Inside Macintosh, which is the defining text for the Macintosh Toolbox
and Operating System.

The book was adapted from "Macintosh C Programming Primer" by the same
authors.  Some traces of C programming practice can be recognized in
the Pascal version.  I found the Pascal style awkward at times.  The
book also contains some serious coding bugs.  Nevertheless, I did learn
a lot from it in very little time.

Let me now be more specific in my comments.  These comments are phrased
as suggestions to the authors, but every reader can benefit from them.


General remarks about the code
- ------- ------- ----- --- ----

    * Instead of

        done := FALSE;
        while (done = FALSE) do begin "statements" end

      at least write

        done := FALSE;
        while not done do begin "statements" end

      but preferrably even write

          done := FALSE;
        repeat "statements" until done

    * Use with-statements to simplify the code; for example, in
      SetUpSizeRect (p.135) you can write:

          procedure SetUpSizeRect;
        begin
        with gSizeRect do begin
            top := MIN_WINDOW_HEIGHT;
            left := MIN_WINDOW_WIDTH;
            bottom := MAXINT;
            right := MAXINT;
            end
        end;

    * Do more error handling right from the beginning (e.g. detecting
      returned nil pointers).  Something like

        procedure Assert(condition:boolean; message:Str255);
        begin
        if not condition then begin
          ShowText;
          writeln(message);
          halt
          end
        end;

      suffices for initial debugging. It need not put up alerts with
      fancy texts.  I once had a problem with a wrong resource ID in
      EventTutor, which does no checking.  For example, in WindowInit
      (p.134) do:

          gPictWindow := GetNewWindow(...);
        Assert(gPictWindow <> nil,'gPictWindow resource not found');


Localized remarks
- --------- -------

p.117    This is C code, instead of Pascal:

        gotOne := GetNextEvent( (mDownMask |
                   keyDownMask), &gTheEvent );

    should read

        gotOne := GetNextEvent( mDownMask + keyDownMask, gTheEvent );

p.129    It might be nice to point out (again) that the project's resource file
    should be set with the Run Options command.

p.129    (First bullet): "You called SelectWindow..."  The code only calls
    SelectWindow in response to a mouseDown event that is inContent.
    So what is the real explanation?

p.132    The constant DRAG_THRESHOLD is not referenced in EventTutor.  What
    is its purpose?  Is something missing?

p.135    Use MAXINT instead of 32767 in SetUpSizeRect.

p.135    Inside Macintosh VI-3-18 recommends a more elaborate approach to
    determine availability of WaitNextEvent.

p.135/6    I had a hard time locating trap numbers (while verifying the code to
    determine availability of WaitNextEvent).  It took me a while to find
    out that they are mentioned in the Appendices of Inside Macintosh
    (its Index is of little help here; I am a real beginning Mac-programmer     :-).  Although there is an official Unimplemented trap, it is
    mentioned only implicitly in Inside Macintosh VI-3-18.  Its actual
    full address is $A89F (cf. Technical Note #156).

p.136    You could simply count the number of null events, instead of showing
    them individually.  N.B. The rate at which null events are received
    also depends on constant SLEEP.

    At first I saw no null events reported after I had uncommented the
    relevant DrawEventString.  This is due to a bug in HandleEvent: the
    line "if gotOne then" should be deleted (gotOne is false when a null
    event is returned by either GetNextEvent or WaitNextEvent).  This
    bug is present on pages 125 and 444 as well.

    I also wondered why I received no keyUp events.  It took me a while
    to figure out that the default global system event mask is set to
    eliminate keyUp events (cf. Inside Macintosh I-254).  Use
    SetEventMask(everyEvent) (cf. Inside Macintosh II-70) on
    initialization to receive keyUp events.

p.138/40  You can use GetWTitle on updateEvt and activateEvt to unify the code,
    thereby avoiding unnecessary duplication.

p.141    N.B. EventTutor needs to do InitCursor to set the cursor from a
    watch to an arrow when it is executed as a stand-alone application.

    By the way, what can you say about memory usage of EventTutor?
    This info is needed to fill out the SIZE resource.

    N.B. EventTutor's method of decoding the osEvt (=app4Evt) message is
    incorrect according to Inside Macintosh VI-5-20.

p.160    N.B. The menu item number returned (implicitly) by MenuSelect is
    the ID stored *inside* the corresponding MENU resource, not the ID
    *of* the resource itself.  Often these IDs are kept the same.  If
    you change the resource ID of a MENU resource, ResEdit will ask you
    (just once) whether you want to change the internal menu ID as well.
    The internal ID can also be changed by opening the resource using a
    template.

    I ran into trouble when I accidentally created MENU resources with
    the wrong IDs and later tried to change them.  First the program
    failed to find the MENU resources (because the IDs in the program
    were not the same as in the resource fork).  After changing them,
    the program still failed to recognize the menu commands (because
    the internal IDs were still wrong).

p.172    In the first comment line, HandleStyleChoice should read CheckStyles.

p.187    According to Inside Macintosh I-355, the low word of the return value
    of MenuSelect is undefined if the high word is zero (no choice
    condition).  Thus the code should read:

        theMenu := HiWord(menuChoice);
        theItem := LoWord(menuChoice);
        if (theMenu <> 0) then begin
            case theMenu of ...

p.221    Again C code instead of Pascal: dialogDone = FALSE should of course
    read dialogDone := FALSE.

p.230    Figure 6.22 contains a typo concerning items 9, 10, and 11 (look at the
    Text fields).

p.246    Align case MINS_RADIO with others.  Here, it would also be appropriate
    to introduce a procedure to toggle a control (again lots of duplicated
    code).

p.251    By looking at the dialog in a slightly different way, DialogInit could
    use RestoreSettings to set it up.  Of course, in that case you need to
    iniitialize the global variables first.  Now there is a lot of code
    duplication.

p.267/8    The text mentions locking the string handle.  This is not done in the
    code.  It also not clear where it should be unlocked again.  Also see
    p.194.  Should the code on p.268 for case SECS_RADIO read

        HLock(Handle(gDefaultSecsH));
        SetIText(itemHandle,gDefaultSecsH^^);
        HUnlock(Handle(gDefaultSecsH));

    and similarly for gDefaultMinsH in MINS_RADIO ?

p.391    Corrections: (1) Desktop file rebuilding is initiated by holding the
    Command and Option keys *when first mounting the volume*.  For the
    boot volume, mounting happens at startup; for floppies, when you
    insert them for the first time.  (2) Rebuilding the desktop file
    erases the Finder's Get Info comment texts for *ALL* files on the
    volume, not just for applications.  [There exist utilities that save
    these Get Info comments before rebuilding and restore them
    afterwards.]  (3) In order to make a new icon show up it is not
    necessary to rebuild the desktop file of the boot volume.  The THINK
    Pascal documentation in fact recommends the following procedure
    [THINK Pascal 3.0 Resource Utilities Manual, p.59]: copy your
    application with its (not yet displaying icon) to a floppy; rebuild
    the desktop of the floppy; copy the application back to your target
    disk; and lo, the new icon shows up (the Finder quietly updates its
    icon info in the desktop file of the target volume as well).

p.392    Should the 'vers' resource be purgeable?  (I guess so, since it is
    not a MENU or MBAR.)  It might be nice to repeat this once more.
    Readers like me hop through the book and either forget earlier
    advice or haven't seen it yet.


These comments cover only those parts of the book that I read more
carefully.  I hope they can be of use to improve the next edition.

    Tom
- --
INTERNET: [e-mail]  /    Eindhoven University of Technology
VOICE: [phone]      /    Dept of Mathematics & Computing Science
FAX: [phone]       /    PO Box 513, NL-5600 MB Eindhoven, Netherlands

+++++++++++++++++++++++++++

From: [e-mail] (Scott Bronson)
Date: 26 Apr 92 16:48:45 GMT

In <[e-mail]> [e-mail] (Tom Verhoeff) writes:
>    * Instead of
>        done := FALSE;
>        while (done = FALSE) do begin "statements" end
>      at least write
>        done := FALSE;
>        while not done do begin "statements" end
>      but preferrably even write
>          done := FALSE;
>        repeat "statements" until done

Only two out of three of these say the same thing.  Notice how in the
first and second examples above, if [not done] evaluates to true, the
code inside your while loop won't be executed even once.  However,
in the third example above, the code inside your repeat loop will
always be executed once, THEN the condition is checked.  A subtle
difference, but it does matter.


    - Scott

+++++++++++++++++++++++++++

From: [e-mail]
Date: 26 Apr 92 22:22:17 GMT
Organization: Actrix Information Exchange

In article <scott.704306925@mcl> [e-mail] (Scott Bronson) writes:
> In <[e-mail]> [e-mail] (Tom Verhoeff) writes:
> >    * Instead of
> >        done := FALSE;
> >        while (done = FALSE) do begin "statements" end
> >      at least write
> >        done := FALSE;
> >        while not done do begin "statements" end
> >      but preferrably even write
> >          done := FALSE;
> >        repeat "statements" until done
>
> Only two out of three of these say the same thing.  Notice how in the
> first and second examples above, if [not done] evaluates to true, the
> code inside your while loop won't be executed even once.  However,
> in the third example above, the code inside your repeat loop will
> always be executed once, THEN the condition is checked.  A subtle
> difference, but it does matter.


Perhaps you didn't notice that done is set to FALSE initially?  The
loop will *always* be executed at least once, whether in the while or
repeat form.

Why test the condition initially when you *know* how it will turn out?

- --
[e-mail]   Twisted pair: [phone]
BIX: brucehoult                 Last Resort:  PO Box 4145 Wellington, NZ
"Cray's producing a 200 MIPS personal computer with 64MB RAM and a 1 GB
hard disk that fits in your pocket!"   "Great!  Is it PC compatable?"

---------------------------

From: [e-mail] (Michael Graf)
Subject: List Box LDEF with icons
Date: 24 Apr 92 18:49:17 GMT
Organization: Australian Programming Centre (IBMA)


  Recently, someone on the net mentioned that there was an Apple Snippet
or sample code available that demonstrated how to write an LDEF (List Manager
defintion ?) which displayed icons alongside the name of the list elements.

  Can anyone point me to where this snippet resides or what set of Apple
Source code snippets it can be found in ?

  Thanx for the help, and to those that answered my previous query.


**********************************************************************
Regards,
  Michael Graf                             ([e-mail])
**********************************************************************

+++++++++++++++++++++++++++

From: [e-mail] (Keith Rollin)
Date: 24 Apr 92 18:56:38 GMT
Organization: Taligent

In article <[e-mail]>, [e-mail]
(Michael Graf) writes:
>
>
>   Recently, someone on the net mentioned that there was an Apple Snippet
> or sample code available that demonstrated how to write an LDEF (List Manager
> defintion ?) which displayed icons alongside the name of the list elements.
>
>   Can anyone point me to where this snippet resides or what set of Apple
> Source code snippets it can be found in ?

Here's an LDEF I wrote that shows selected items as checked, rather than
hilited. It uses two 'sicn's to draw the two states of the checkbox. The
resource ID's for the two icons are stored in the upper and lower words of the
list's refcon. PlotIconID() is from Technote #306.

//--------------------------------------------------------------------------

pascal void main(    short        lMessage,        // what operation to do
                    Boolean        lSelect,        // draw it selected?
                    Rect*        lRect,            // where to draw the item
                    Cell        lCell,            // which cell to draw
                    short        lDataOffset,    // offset to data for drawing
                    short        lDataLen,        // length of that data
                    ListHandle    lHandle)        // handle to list record
{
    FontInfo        info;
    ListPtr            listPtr;
    Rect            iconRect;
    Point            textLocation;
    DataHandle        listCells;
    unsigned char    oldState;

    switch (lMessage) {
        case lInitMsg:
            GetFontInfo(&info);
            listPtr = *lHandle;
            if (listPtr->cellSize.v < 16)
                listPtr->cellSize.v = 16;
            listPtr->indent.h = listPtr->cellSize.v - info.leading;
            listPtr->indent.v = listPtr->indent.h - info.descent;
            break;

        case lDrawMsg:

            PenNormal();
            EraseRect(lRect);

            PlotCheckBox(lRect, lHandle, lSelect);

            if (lDataLen > 0) {
                textLocation.h = 4 + 16 + 4;
                textLocation.v = lRect->top + (**lHandle).indent.v;
                MoveTo(textLocation.h, textLocation.v);

                listCells = (**lHandle).cells;
                oldState = HGetState(listCells);
                HLock(listCells);
                DrawText((*listCells) + lDataOffset, 0, lDataLen);
                HSetState(listCells, oldState);
            }

            break;

        case lHiliteMsg:
            PlotCheckBox(lRect, lHandle, lSelect);
            break;
    }
}


void    PlotCheckBox(Rect* lRect, ListHandle lHandle, Boolean lSelect)
{
    Rect    iconRect;
    long    refCon;
    short    iconID;

    iconRect.left = 4;
    iconRect.bottom = lRect->top + (**lHandle).indent.h;
    iconRect.right = iconRect.left + 16;
    iconRect.top = iconRect.bottom - 16;
    refCon = (**lHandle).refCon;
    iconID = (lSelect ? HiWord(refCon) : (short) refCon);
    PlotIconID(&iconRect, atNone, ttNone, iconID);
}


- --
Keith Rollin
Phantom Programmer
Taligent, Inc.


---------------------------

From: [e-mail] (Andrew E Page)
Subject: Precompiled version of MacApp.h
Date: 8 Apr 92 14:07:13 GMT
Organization: The World Public Access UNIX, Brookline, MA


   With alot of cursing and some fidling around I've managed to produce
a precompiled version of MacApp.h.  I had to crank the partition of
MPW Shell up to 9 Meg in order to do this and the resulting file is
about 2.3 Meg long.

   Would anyone be interested in having me post this to AppleLink
or UUEncode it for the net?


- --
Andrew E. Page CTO(Warrior Poet)|   Decision and Effort The Archer and Arrow
DSP Ironworks                   |     The difference between what we are
Macintosh and DSP Technology    |           and what we want to be.

+++++++++++++++++++++++++++

From: [e-mail] (Mark Lanett)
Date: 8 Apr 92 15:05:10 GMT
Organization: University of Illinois at Urbana

[e-mail] (Andrew E Page) writes:

>   With alot of cursing and some fidling around I've managed to produce
>a precompiled version of MacApp.h.  I had to crank the partition of
>MPW Shell up to 9 Meg in order to do this and the resulting file is
>about 2.3 Meg long.

All it takes is doing an "MABuild -CPlusLoad" and adding
"{OtherLinkFiles} f {CPlusLoad}" to the .MAMakefile...

You might want to add '-CPlus -mf -Link -mf' to your MABuildDefaults in
{MacApp}"Startup Files:Startup". Then you can drop your shell
partition to 3Mb again and let it go to MultiFinder for the rest.
The -CPlusLoad can be added there also.

>   Would anyone be interested in having me post this to AppleLink
>or UUEncode it for the net?

Wouldn't do anyone else any good since (a) it is compiled for specific
MABuild options, and (b) contains full pathnames.
- --
Mark Lanett, Software Tools Group, NCSA           [e-mail] or  NCSA.STG
"People wander in and out of virtual rooms in virtual settings with virtual
characters and virtual money and virtual armor and virtual weapons, which is
virtually a good way to spend time, but not quite." -- Usenet Oracle
- --
Mark Lanett, Software Tools Group, NCSA           [e-mail] or  NCSA.STG
"People wander in and out of virtual rooms in virtual settings with virtual
characters and virtual money and virtual armor and virtual weapons, which is
virtually a good way to spend time, but not quite." -- Usenet Oracle

+++++++++++++++++++++++++++

From: [e-mail] (Kent Sandvik)
Date: 14 Apr 92 19:41:21 GMT
Organization: MacDTS Mongols

In article <[e-mail]>, [e-mail]
(Mark Lanett) writes:
>
> [e-mail] (Andrew E Page) writes:
>
> >   With alot of cursing and some fidling around I've managed to produce
> >a precompiled version of MacApp.h.  I had to crank the partition of
> >MPW Shell up to 9 Meg in order to do this and the resulting file is
> >about 2.3 Meg long.
>
> All it takes is doing an "MABuild -CPlusLoad" and adding
> "{OtherLinkFiles} f {CPlusLoad}" to the .MAMakefile...
>
> You might want to add '-CPlus -mf -Link -mf' to your MABuildDefaults in
> {MacApp}"Startup Files:Startup". Then you can drop your shell
> partition to 3Mb again and let it go to MultiFinder for the rest.
> The -CPlusLoad can be added there also.

Yes, I've seen people misusing the MPW shell partition sizes, a simple
performance test would show how little this really helps if you use -mf.
I wrote a TN about performance, and based on my tests I saw that the
performance gains with large shells is marginal, if not actually missing.
The -mf flag is really useful, because memory is then only used for
peak activities, like when the Cfront compiler kicks in. Have Swatch up
and running while you compile and you will see how this all works.

As for the MacApp header dump, yes MacApp 3.0 has the -CPlusLoad flag
defined as default, so you can't avoid using pre-compiled headers :-).
(same with -mf, it's also default for all the tools that understands
the flag).

Cheers,
Kent Sandvik/dTs

+++++++++++++++++++++++++++

From: [e-mail] ( )
Date: 18 Apr 92 22:25:42 GMT

In <[e-mail]> [e-mail] (Kent Sandvik) writes:
>The -mf flag is really useful, because memory is then only used for
>peak activities, like when the Cfront compiler kicks in. Have Swatch up
>and running while you compile and you will see how this all works.

But is there a version of Swatch that works on the Quadras?
Mine will run, but it says "bad bad bad bad..." where the stack structures
are supposted to be drawn.

- --
=  Marc Tamsky    [e-mail]    KB6JWE  =

+++++++++++++++++++++++++++

From: [e-mail] (Jon W{tte)
Date: 19 Apr 92 09:41:21 GMT
Organization: Royal Institute of Technology, Stockholm, Sweden

> [e-mail] ( ) writes:

   But is there a version of Swatch that works on the Quadras?

Mine runs just fine. It's version 1.2.2.

- --
"You should meet yourself someday. I'm sure you would hate it."
- - Me: [e-mail]; Jon W{tte (The Diplomat - NOT!)

+++++++++++++++++++++++++++

From: [e-mail] (Kent Sandvik)
Date: 21 Apr 92 23:02:39 GMT
Organization: MacDTS Mongols

In article <u_banzai.703635942@mcl>, [e-mail] ( ) writes:
>
> In <[e-mail]> [e-mail] (Kent Sandvik) writes:
> >The -mf flag is really useful, because memory is then only used for
> >peak activities, like when the Cfront compiler kicks in. Have Swatch up
> >and running while you compile and you will see how this all works.
>
> But is there a version of Swatch that works on the Quadras?
> Mine will run, but it says "bad bad bad bad..." where the stack structures
> are supposted to be drawn.

Hmm, Swatch 1.2.2 and 1.7d5 (the one that shows the MultiFinder heap) seems
to work fine with my Quadra. I don't run VM. Anyway, About Macintosh
is a more crude way to watch MF memory use.

Cheers,
Kent

+++++++++++++++++++++++++++

From: [e-mail] (Jamie R. McCarthy)
Date: 22 Apr 92 14:14:14 GMT
Organization: Kalamazoo College

[e-mail] (Kent Sandvik) writes:
>[e-mail] ( ) writes:
>>
>> But is there a version of Swatch that works on the Quadras?
>> Mine will run, but it says "bad bad bad bad..." where the stack structures
>> are supposted to be drawn.
>
>Hmm, Swatch 1.2.2 and 1.7d5 (the one that shows the MultiFinder heap) seems
>to work fine with my Quadra.

GateKeeper versions before 1.2.5 corrupt the System heap so delicately
that (apparently) only Swatch and the Think Pascal debugger picked up on
it.  1.2.5 fixes it.  Could this be your problem?
- --
 Jamie McCarthy     Internet: [e-mail]     AppleLink: j.mccarthy
 Youth culture killed my dog...

+++++++++++++++++++++++++++

From: [e-mail] (Dave Ely)
Organization: Symantec / Peter Norton
Date: Sat, 25 Apr 1992 03:03:29 GMT

[e-mail] (Kent Sandvik) writes:
> In article <u_banzai.703635942@mcl>, [e-mail] ( ) writes:
> > But is there a version of Swatch that works on the Quadras?
> > Mine will run, but it says "bad bad bad bad..." where the stack structures
> > are supposted to be drawn.
>
> Hmm, Swatch 1.2.2 and 1.7d5 (the one that shows the MultiFinder heap) seems
> to work fine with my Quadra. I don't run VM. Anyway, About Macintosh
> is a more crude way to watch MF memory use.

Swatch 1.2.2 does not like 32 bit mode heaps. Go back to 24 bit mode for
heap testing.

What was the 1.7d5 thing that shows the MultiFinder heap? Is that a newer
version of Swatch?
- --
 ______________________________________________________________
    Dave Ely                    | Internet:  [e-mail]
    Symantec/Peter Norton Group | AppleLink: Ely.D

---------------------------

From: [e-mail] (Marshall Gilula)
Subject: ResEdit and 7.0
Date: 24 Apr 92 07:05:33 GMT


One of my favorite tiny hacks is on the "Special" menu bar item to
permit myself to use Command-F (for "Flush") for emptying the trash, etc.
I have ResEdit 2.1.1 and both the Reference manual from APDA and the
longer detailed book on Resedit, AND the assistance of one of my best
hacker friends (he was familiar with the 2.XX Resedit) but neither of
us could ever find the Special menu .

help!

Marshall Gilula
[e-mail]


In pre-7.0 systems I was able to do the hack.

+++++++++++++++++++++++++++

From: [e-mail] (Sting)
Date: 24 Apr 92 12:57:30 GMT
Organization: Dartmouth College, Hanover, NH

In <[e-mail]> [e-mail] (Marshall Gilula) writes:


>One of my favorite tiny hacks is on the "Special" menu bar item to
>permit myself to use Command-F (for "Flush") for emptying the trash, etc.
>I have ResEdit 2.1.1 and both the Reference manual from APDA and the
>longer detailed book on Resedit, AND the assistance of one of my best
>hacker friends (he was familiar with the 2.XX Resedit) but neither of
>us could ever find the Special menu .

>help!

>Marshall Gilula
>[e-mail]

The reason you could do this in previous systems is that they used MENU
resources for the finder menus.  Under System 7, there are 'fmnu' resources
which contain not only the items and their cmd-key equivalents, but also
the appleEvents they are associated with.

You can get a ResEdit 'fmnu' template from various anonymous ftp sites (try
ftp.apple.com).  This should allow you to do this hack.

AppleEvents are very cool...you can add a "quit" command to the finder that
actually MAKES IT QUIT without having to hack around in the CODE segments.
Can't do that under previous systems!

Ciao!
Mike


- --
Michael J. Fromberger            | Take a look at my new toy,
Composer, Guitarist            | It'll blow your head in two, oh boy!
[e-mail]                | Truth hits everybody
  friendly email welcome!!         | Truth hits everyone...  (The Police)

+++++++++++++++++++++++++++

From: [e-mail]
Date: 24 Apr 92 14:45:22 GMT
Organization: BC Systems Corporation

In article <[e-mail]>, [e-mail] (Marshall Gilula) writes:
>
> One of my favorite tiny hacks is on the "Special" menu bar item to
> permit myself to use Command-F (for "Flush") for emptying the trash, etc.
> I have ResEdit 2.1.1 and both the Reference manual from APDA and the
> longer detailed book on Resedit, AND the assistance of one of my best
> hacker friends (he was familiar with the 2.XX Resedit) but neither of
> us could ever find the Special menu .
>
> help!
>
> Marshall Gilula
> [e-mail]
>
>
> In pre-7.0 systems I was able to do the hack.

That's right, in pre 7.0 systems, you can find the menu.  In system 7, it's in
the 'fmnu' resource.  Actually, a recent article in MacUser (2 to 3 months ago)
told you how to do it!!!  I can't remember the resource numbers and such, but
it is there because I've done it in my system.  I also use cmd-S for Shutdown
and cmd-R for restart!!! Comes in handy.

There are a set of extensions for ResEdit that will allow you to see the 'fmnu'
resource like a STR resource (or something like that) out there on many ftp
sites.  I posted this set to the net last year as well, but got flamed because
many ppl asked for them but I shouldn't have posted them to c.s.m.p.  However,
I did send them to c.s.m.binaries, they just never showed up!!!!

- --
[e-mail]
Victoria, British Columbia, Canada

---------------------------

End of C.S.M.P. Digest
**********************